Skip to content

Conversation

@BYK
Copy link
Member

@BYK BYK commented Jan 9, 2026

Summary

This PR migrates from the deprecated action-prepare-release to the new Craft GitHub Actions.

Changes

  • Migrated .github/workflows/auto-release.yml to Craft reusable workflow

Documentation

See https://getsentry.github.io/craft/github-actions/ for more information.

Closes #18765 (added automatically)

This PR migrates from the deprecated action-prepare-release to the new
Craft GitHub Actions (reusable workflow or composite action).

Changes:
- Migrate .github/workflows/release.yml to Craft reusable workflow
@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 2026

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

  • (core) Add ignored client report event drop reason by Lms24 in #18815

Build / dependencies / internal 🔧

  • (release) Switch from action-prepare-release to Craft by BYK in #18763

🤖 This preview updates automatically when you update the PR.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 9, 2026

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 9,027 - 9,512 -5%
GET With Sentry 1,641 18% 1,616 +2%
GET With Sentry (error only) 6,138 68% 6,033 +2%
POST Baseline 1,189 - 1,197 -1%
POST With Sentry 584 49% 590 -1%
POST With Sentry (error only) 1,032 87% 1,051 -2%
MYSQL Baseline 3,237 - 3,335 -3%
MYSQL With Sentry 432 13% 464 -7%
MYSQL With Sentry (error only) 2,676 83% 2,689 -0%

View base workflow run

BYK added 2 commits January 9, 2026 23:16
The previous migration incorrectly removed the GitHub App token
authentication step. This commit restores it by switching to the
composite action pattern which preserves the auth flow.
The previous migration incorrectly removed the GitHub App token
authentication step. This commit restores it by switching to the
composite action pattern which preserves the auth flow.
Comment on lines 2 to 9
on:
pull_request:
types:
- closed
branches:
- master

# This workflow tirggers a release when merging a branch with the pattern `prepare-release/VERSION` into master.
workflow_dispatch:
inputs:
version:
description: Version to release (or "auto")
required: false
force:
description: Force a release even when there are release-blockers

This comment was marked as outdated.

Comment on lines 2 to 11
on:
pull_request:
types:
- closed
branches:
- master
workflow_dispatch:
inputs:
version:
description: Version to release (or "auto")
required: false
force:
description: Force a release even when there are release-blockers
required: false
merge_target:

This comment was marked as outdated.

Comment on lines 33 to 41
- name: Prepare release
uses: getsentry/craft@39ee616a6a58dc64797feecb145d66770492b66c # v2
env:
GITHUB_TOKEN: ${{ steps.token.outputs.token }}
with:
version: ${{ inputs.version }}
force: ${{ inputs.force }}
merge_target: ${{ inputs.merge_target }}
craft_config_from_merge_target: 'true'

This comment was marked as outdated.

Copy link
Member Author

@BYK BYK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

update stuff

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

node-version-file: 'package.json'
- name: Prepare release
uses: getsentry/action-prepare-release@v1
uses: getsentry/craft@5d154a7facb096e38889be2c6caf2fd23649aa92# v2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing space before comment makes ref invalid

High Severity

The uses value getsentry/craft@5d154a7facb096e38889be2c6caf2fd23649aa92# v2 is missing a space before #. In YAML, # only starts a comment when preceded by whitespace. Without the space, # v2 becomes part of the ref string, resulting in the invalid git ref 5d154a7facb096e38889be2c6caf2fd23649aa92# v2. This will cause the release workflow to fail every time. Compare with line 26 which correctly uses a space: ...f6c875baf # v2.2.1.

Fix in Cursor Fix in Web

Comment on lines 36 to 42
with:
node-version-file: 'package.json'
- name: Prepare release
uses: getsentry/action-prepare-release@v1
uses: getsentry/craft@5d154a7facb096e38889be2c6caf2fd23649aa92# v2
env:
GITHUB_TOKEN: ${{ steps.token.outputs.token }}
with:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The auto-release.yml workflow was not migrated to the new Craft action and still uses the deprecated getsentry/action-prepare-release@v1, contrary to the PR's description.
Severity: HIGH

Suggested Fix

Update the .github/workflows/auto-release.yml file to use the new Craft reusable workflow, similar to the changes made in .github/workflows/release.yml. This will ensure both manual and automated release processes are consistent and no longer rely on the deprecated getsentry/action-prepare-release@v1 action.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/release.yml#L36-L42

Potential issue: The pull request claims to migrate release workflows to the new Craft
action, but the `auto-release.yml` file was not updated. This file, which triggers an
automated release process when a `prepare-release/*` branch is merged, continues to use
the deprecated `getsentry/action-prepare-release@v1` action. This creates an
inconsistency with the manually triggered `release.yml` workflow, which was correctly
updated. The continued use of the deprecated action poses a risk of failure for the
automated release process if the action is removed or becomes unmaintained.

Did we get this right? 👍 / 👎 to inform future reviews.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 12, 2026

Codecov Results 📊


Generated by Codecov Action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci(release): Switch from action-prepare-release to Craft

2 participants